home *** CD-ROM | disk | FTP | other *** search
- Path: mayne.ugrad.cs.ubc.ca!not-for-mail
- From: c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku)
- Newsgroups: comp.lang.c
- Subject: Re: Sending CTRL-C over a serial line?
- Date: 27 Mar 1996 12:21:05 -0800
- Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
- Message-ID: <4jc7vhINN7nh@mayne.ugrad.cs.ubc.ca>
- References: <4ja0hq$91n@news.oscs.montana.edu>
- NNTP-Posting-Host: mayne.ugrad.cs.ubc.ca
-
- In article <4ja0hq$91n@news.oscs.montana.edu>,
- <gko2708@msu.oscs.montana.edu> wrote:
- >Hey,
- >Can anyone tell me how to send a Ctrl-C over a serial line to another PC
- >ad..and then have that PC respond as if it came from its own keyboard?
-
- You run Linux on the remote machine. The terminal driver sends signals to the
- foreground process group of the session associated with that tty, facilitating
- job control.
-
- Oh, you aren't running a PC UNIX? Too bad.
-
- >I have all of the serial stuff taken care of and I have trapped the CTRl-C on
- >the sending end. I can easily send a 0x03 to the other machine but it does not
- >seem to trigger the interupt. I have seen some info on a CTRL-C flag but i do
- >not have enough to go on. My sending and receiving programs are capable of
- >sending and reeiving a scancode byte and an ASCII byte. Thanks for any help.
-
- Like in UNIX, your remote serial driver has to generate the ``interrupt'' when
- it ``sees'' an 0x3. It's not going to happen by itself!
- --
-
-